Hello, and welcome to
another exciting lesson. Imagine being able to build your own app. Wouldn't
that be amazing? Well, this lesson will
allow you to look at various aspects of building
a model-driven app. You'll get to show off
some of your skills as you learn how
to add dashboards, forms, views, and
charts to your apps. Are you excited
yet? I know I am. This lesson will teach you
everything you need to know about identifying what
model-driven apps are, and how they are different
from canvas apps. Exploring the building
blocks of model-driven apps, creating and designing
model-driven apps, and analyzing how to change security and share
model-driven apps. Let's get right to it. Previously you
explored canvas apps. Now let's take a quick
tour of model-driven apps, and how they differ
from canvas apps. Canvas apps allow you to have complete control over
the layout of the app. With model-driven apps, the layout is
determined for you, and largely designated by the components you
add to the app. But wait, there's more. Model-driven apps help you to quickly view your business data to speed up decision-making instead of creating
complex apps. The good news is, you don't have to be a coding
expert to do this. Just like building a house, there are certain design phases to building a model-driven app. These include modeling
your business data, defining your
business processes, and then finally,
building the app. You'll get to unpack each
of these phases next. Model-driven design uses
metadata driven architecture. In simple terms, this
means that you can customize your app without
having to write code. Before we continue, you might be wondering
what is metadata. Metadata means data about data. It defines the structure
of the data that is stored in the
Microsoft Dataverse. Now that you
understand metadata, let's see how business
data is modeled. It might seem like a
difficult process, but it can be
summarized very easily. To model business data, you simply determine two things. What data the app will need, and how would that data
will relate to other data. Next, you'll explore
defining business processes. The key aspect of
model-driven app design is defining and enforcing
consistent business processes. That's quite a mouthful.
Let's break it down. Consistent processes help ensure that your app users can focus on their work and not
worry about having to remember to perform a
set of manual steps. As you might know, processes
can be simple or complex, and they often change over time. Without further delay, let's see what it means
to build the app. Once you've modeled your data
and defined your processes, you can start to build your app. To do this, you'll
need to select and set up the components you
need in the app designer. Well-done in completing
this lesson. Before you can build your app, it's important to get your
building blocks ready first. See you soon.